ToDo:

1. add syntax rules to all tokenfiles

2. rework following tokenfiles:
	TokenList_WaterlooBasic.txt (double IF statement in BasicV2-Import and here!)
	
3. check all tokenfiles against real programs/machines

4. add configuration dialog with all options

5. Scrollbars

6. Character editor

7. Screen editor

8. mark text with mouse

9. Import & Renumber from other file

10. Snippet library

11. Sprite Editor (C64)

12. Interface/API to external tools

13. "0 REM ExBASIC Level-II" write & detect for token list

14. compact lines : DATAs intelligent combine

15. red line at 80/88 columns

16. auto indent in label mode

17. More fileformats (P00, ...)


(fail -> AbraXxl) Make BasEdit Mono-kompatible

-----------------------------------------------------------------------------------------------
1.42:
(OK) lots of bugfixes for syntax check

(OK) tokenization bug fixed (FORI=CSTOCS)

(OK) better handling of ' comment in tokenization and code generation

-----------------------------------------------------------------------------------------------
1.41:

(OK) bugfix for PRINTCHR$(147) - couldn't evaluate the parameter in parenthesis

-----------------------------------------------------------------------------------------------
1.40:

(OK) ^ and ? will be now correct when exporting as ASCII 

(OK) new setting in BasEdit.Ini: KeyMap=KeyMap.txt 

(OK) Syntax check now gives the opportunity to ignore an error and resume with the next line 

-----------------------------------------------------------------------------------------------
1.39:

(OK) Option Strict enabled

-----------------------------------------------------------------------------------------------
1.38:

(OK) Basic extensions in project mode

-----------------------------------------------------------------------------------------------
1.37:

(OK) fixed wrong starting directory when started with drag'n drop from file explorer

-----------------------------------------------------------------------------------------------
1.36:

(OK) pathes for Fonts, tokenizers etc. are based on application directory

-----------------------------------------------------------------------------------------------
1.35:

(OK) J0=(LEFT$(A$,1)="Y")

(OK) Scientific notation for numbers

(OK) {sh asterisk} inserted as CHR$92) instead of CHR$(192)

-----------------------------------------------------------------------------------------------
1.34:

(OK) Special treatment of ' comments in Label-mode if not HasSimpleRem in tokenfile

-----------------------------------------------------------------------------------------------
1.33:

(OK) Open Diskmanager when started with Dxx only

(OK) Drag'n Drop txt-files to Editor : Ask for ASCII & Tokenizer or PETSCII

(OK) "Project files"

-----------------------------------------------------------------------------------------------
1.32:

(OK) Support for D71 and D81 Diskimages

-----------------------------------------------------------------------------------------------
1.30:

(OK) disk file dialog: double-click to load

(OK) disk management dialog (copy, del, rename, etc.)

(OK) Syntax rule for DIMA(1),B(2),...

(OK) check for DiskImage writeable before real write attempt

(OK) DiskImage: overwrite existing sectors on save 

-----------------------------------------------------------------------------------------------
Diddl / FE3:

Feature Anfrage:

Die Final Expansion wird mit kurzen "BASIC" Programmen konfiguriert. 
Natrlich sind das keine richtigen BASIC Programme aber Konfigurationstext (siehe LOADER Doku) 
der als VC-20 BASIC gespeichert wird.

Man kann ja jetzt schon mit deinem Tool sehr gut diese LOADER Dateien erstellen. 
Aber natrlich knnte man am PC noch ganz andere Vorteile nutzen: 
Kleine Dialogbox wo man einen Abschnitt komplett definiert

Analyse der gewhlten Dateien und so einen Vorschlag der Konfiguration.

sofortiger Test im VICE (die Final Expansion wird vom VICE emuliert)

D64 erstellen

Eine Bibliothek der Konfigurationen:

Die Konfigurationen knnte man in einer "Bibliothek" sammeln und unter allen FE3 Benutzern austauschen. 
Wenn man VC-20 Programmdateien auswhlt knnte man automatisch passende Konfigurationen finden. 
Entweder manuell oder sogar durch Prfsummen.


	